<?php
/**
 * <https://y.st./>
 * Copyright © 2019 Alex Yst <mailto:copyright@y.st>
 * 
 * This program is free software: you can redistribute it and/or modify
 * it under the terms of the GNU General Public License as published by
 * the Free Software Foundation, either version 3 of the License, or
 * (at your option) any later version.
 * 
 * This program is distributed in the hope that it will be useful,
 * but WITHOUT ANY WARRANTY; without even the implied warranty of
 * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
 * GNU General Public License for more details.
 * 
 * You should have received a copy of the GNU General Public License
 * along with this program. If not, see <https://www.gnu.org./licenses/>.
**/

$xhtml = array(
	'<{title}>' => 'Futile',
	'takedown' => '2017-11-01',
	'<{body}>' => <<<END
<img src="/img/CC_BY-SA_4.0/y.st./weblog/2019/01/02.jpg" alt="The end of the sidewalk" class="framed-centred-image" width="649" height="480"/>
<section id="drudgery">
	<h2>Drudgery</h2>
	<p>
		My discussion posts for the day:
	</p>
	<blockquote>
		<p>
			I like the way you phrased that.
			In a $a[FIFO] buffer pool, the buffer to have its data purged to make room for new data is indeed the one that&apos;s held its current data the longest.
			Like you said though, when the initial time the data was accessed has little to do with if or when it&apos;ll be accessed again, a $a[FIFO] buffer pool isn&apos;t very efficient.
			It does work fine when data is used sequentially though.
		</p>
	</blockquote>
	<blockquote>
		<p>
			I don&apos;t know about for you, but for me, the concept of binding an expression (not a value) to a variable is a strange one.
			Lazy evaluation has odd quirks like that which are easy enough to understand, but yet go against the standard flow of things so much that it seems difficult to program that way.
			It&apos;s just something we need to account for and get used to, I suppose.
			It&apos;s like when I write in Lua.
			One of the mistakes I often make is assuming that tables are indexed from zero like they should be.
			But in Lua, tables are bizarrely indexed from one, and attempting to index from zero causes various unexpected behaviours, depending on the context.
			It&apos;s easy enough to index from one, but when I forget to do that, I get all sorts of odd bugs in my code.
		</p>
	</blockquote>
</section>
<section id="Minetest">
	<h2>Minetest</h2>
	<p>
		I&apos;m starting to think trying to craft Minetest into the perfect game for me using mods is a futile effort.
		Even once I get the gameplay perfect, there&apos;s still one fatal flaw: multi-player support is provided only via an unencrypted channel.
		And Minetest isn&apos;t the sort of game I like to play alone.
	</p>
</section>
END
);
